Summary

convertToProcessedStreamResponse in plugins/logging/utils.go has a switch on requestType that covers six request types but is missing a case for schemas.WebSocketResponsesRequest. Requests routed through the native-WS Responses path fall through to default and get stored under streaming.StreamTypeChat instead of streaming.StreamTypeResponses. This mis-labels the accumulated chunk data in the log store, causing downstream consumers that branch on stream type to receive incorrectly shaped content for WebSocket Responses streams.

Root cause: schemas.WebSocketResponsesRequest was added after the switch was written and the case was never added.

Changes

• plugins/logging/utils.go: extend the ResponsesStreamRequest case to also match schemas.WebSocketResponsesRequest, routing it to streaming.StreamTypeResponses.
• plugins/logging/utils_test.go: add five unit tests covering the new case, a regression guard for the existing ResponsesStreamRequest arm, a parity assertion between both types, nil-input safety, and the default fallback.

Type of change

• Bug fix

Affected areas

• Plugins

How to test

go build ./plugins/logging/...
go test ./plugins/logging/... -cover -run TestConvertToProcessed
go vet ./plugins/logging/...

Expected: all five TestConvertToProcessed* tests pass. WebSocketResponsesRequest and ResponsesStreamRequest both resolve to streaming.StreamTypeResponses.

Runtime validation requires #2997 and #2999 to land first (those PRs restore the WS log row write path on main). Once they are in, the steps from the issue reproduce the correct stream_type = responses in the stored row.

Screenshots/Recordings

N/A (logging internals, no UI change)

Breaking changes

• No

Related issues

Closes #3000

Related: #2997 and #2999 are prerequisites for runtime observation of this defect (they restore the WS log row write path on main). This bug was discovered while working on PR #2775 in thiscantbeserious/bifrost. That branch contains the fix extracted here as a side effect of the feature work.

Security considerations

None. This change only affects how an existing log accumulation result is categorised by stream type.

Checklist

• I read docs/contributing/README.md and followed the guidelines
• I added/updated tests where appropriate
• I updated documentation where needed
• I verified builds succeed (Go and UI)
• I verified the CI pipeline passes locally if applicable